Contribution org.nuxeo.ecm.core.storage.dbs.migrator--configuration
In component org.nuxeo.ecm.core.storage.dbs.migrator
org.nuxeo.ecm.core.storage.dbs.migrator
inside nuxeo-core-storage-dbs-2021.62.7.jar /OSGI-INF/dbs-blob-keys-migration.xml
You can influence this order by adding "require" tags in the containing component declaration, to make sure it is resolved after another component (see "Resolution Order" on components).
This contribution is part of XML component Extension Point
Extension point configuration of component MigrationService.Registration Order
1
The registration order represents the order in which this contribution was registered on its target extention
point.
This will impact the override/merge behaviour when it is implemented on the target service, and is useful for
proper customization of existing contributions.
You can influence this order by adding "require" tags in the containing component declaration, to make sure it is resolved after another component (see "Resolution Order" on components).
Contributed Items
XML Source
<extension point="configuration" target="org.nuxeo.runtime.migration.MigrationService">
<migration id="blob-keys-migration">
<description label="migration.dbs.blob.keys">Populate ecm:blobKeys property</description>
<class>org.nuxeo.ecm.core.storage.dbs.BlobKeysBulkMigrator</class>
<defaultState>unsupported</defaultState>
<state id="unsupported">
</state>
<state id="empty">
<description label="migration.dbs.blob.keys.empty">ecm:blobKeys is not populated</description>
</state>
<state id="populated">
<description label="migration.dbs.blob.keys.populated">ecm:blobKeys is populated</description>
</state>
<step fromState="empty" id="empty-to-populated" toState="populated">
<description label="migration.dbs.blob.keys.empty-to-populated">Populate ecm:blobKeys property</description>
</step>
</migration>
</extension>